Monitoring Services

Within the frame of the Service Level Management functionality, the Monitor is the control center of the services (executable objects) defined in the SLO (Service Level Objectives) objects. It provides timely information on the status of the services (the tasks).

SLO objects depict the parties and requirements involved in a Service Level Agreement as follows:

They define the beneficiaries; these are the departments, business units, etc. that require the service as stipulated in the agreement. They are defined via custom attributes and can be assigned to the objects (services) as Custom Attributes.
They also define the service that must be provided, that is, the objects or groups of objects whose execution results are the subjects of the agreement.
They determine the criteria that the execution of the services must meet.
They specify the actions that will be taken in case the requirements are fulfilled or violated.

Based on the parameters defined in an SLO object, the behavior of the services (tasks) is monitored; if any of the criteria is not met, this is indicated at the earliest possible time. Likewise, the Monitor also informs of criteria that are satisfied.

If activated, the services in an SLO object are monitored either 24/7 or within a specific daily time frame, depending on its configuration.

This is how the Service - Fulfillments table in the Process Monitoring perspective looks like:

What SLM Checks

The SLO object stipulates the criteria that must be met when executing the services. According to this, the following parameters can be monitored:

Runtime

The behavior of a service (a task or group of tasks) can be monitored based on its runtime settings (MRT/SRT). These are specified on the Runtime Page when defining an object. The SLO object can be configured to check whether the services are executed

within the Maximum Runtime (MRT) specified for the objects

This means that the execution of the service cannot take longer that the Maximum Runtime specified in the object definition.

If it runs longer than that, a violation is generated immediately. This check is performed based on the Automation Engine-internal timer interval defined in UC_JOB_CHECKINTERVAL (see UC_JOB_CHECKINTERVAL - Periodic Time Check in the Automation Engine).
over the Minimum Runtime (SRT) specified for the objects

This means that the execution of the service must take longer than the Minimum Runtime specified in the object definition.

If it runs shorter than that, a violation is generated at service end.

End status

The behavior of a service can also be monitored based on the end status of the tasks. If the service ends with a status other than the specified one, a violation is generated.

Time/Weekdays

The SLO object can also determine the times/weekdays on which the services should start and/or end at the latest.

If the latest start/end time of a service deviates from the specified ones, a violation is generated as soon as the indicated latest end time is reached. This check happens at full minutes (hh:mm:00 seconds).